Changes are coming to https://stigviewer.com.
Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey
Chrome development tools must be disabled.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
|---|---|---|---|---|
| V-221599 | DTBC-0068 | SV-221599r615937_rule | Low |
| Description |
|---|
| While the risk associated with browser development tools is more related to the proper design of a web application, a risk vector remains within the browser. The developer tools allow end users and application developers to view and edit all types of web application related data via the browser. Page elements, source code, javascript, API calls, application data, etc. may all be viewed and potentially manipulated. Manipulation could be useful for troubleshooting legitimate issues, and this may be performed in a development environment. Manipulation could also be malicious and must be addressed. |
| STIG | Date |
|---|---|
| Google Chrome Current Windows Security Technical Implementation Guide | 2022-11-28 |
Details
| Check Text ( C-23314r478214_chk ) |
|---|
| Universal method: 1. In the omnibox (address bar) type chrome://policy 2. If the policy "DeveloperToolsAvailability" is not shown or is not set to "2", this is a finding. Windows method: 1. Start regedit 2. Navigate to HKLM\Software\Policies\Google\Chrome\ 3. If the key "DeveloperToolsAvailability" does not exist or is not set to "2", this is a finding. |
| Fix Text (F-23303r478215_fix) |
|---|
| Windows group policy: 1. Open the "group policy editor" tool with gpedit.msc 2. Navigate to Policy Path: Computer Configuration\Administrative Templates\Google\Google Chrome Policy Name: Control where Developer Tools can be used Policy State: Enabled Policy Value: Disallow usage of the Developer Tools |